《Cursor Docs》-Work with Grok Bot
Everything about working with Bots day to day: creating and managing them, messaging and collaborating, the computer they share, and turning finished work into skills and routines.
Read More《Cursor Docs》-Grok Bot use cases
The best Bot roles own a repeatable outcome, not a loose category of questions. Start each role with read and prepare work, review the result, and only then add approved actions or a routine.
Read More《Cursor Docs》-Grok Bot for Teams and Enterprise
Grok Bot gives each person on your team standing Bots for everyday work: research, operations, documents, browsing, and automations. This page is for team and organization admins rolling Grok Bot out. Security reviewers should start with Grok Bot security and the Grok Bot security FAQ. Members who want the approval model should start there too.
Read More《Cursor Docs》-Settings and notifications
Grok Bot settings cover app wide and desktop local behavior. Each Bot's profile and notification preference live in its conversation details. Open settings from the account menu or with Cmd+,.
Read More《Cursor Docs》-Grok Bot security FAQ
These are the questions security reviews ask most often. The controls behind each answer are on Grok Bot security. Dashboard settings and rollout steps are on Grok Bot for Teams and Enterprise.
Read More《Cursor Docs》-Grok Bot security
Use these controls and deployment details to decide whether Grok Bot is allowed in, and to limit what Bots can access, change, and retain. Rollout steps and the dashboard settings list live on Grok Bot for Teams and Enterprise. Common review questions are on Grok Bot security FAQ.
Read More《Cursor Docs》-Configure TLS-inspecting proxies
The Grok Bot desktop app connects from each member's device to two places: Cursor's API at .cursor.sh for chat, sign in, and approvals, and the member's hosted computer at a nested . .cursorvm.com hostname for computer setup, screen, and shell. Secure web gateways that inspect TLS often let the first through and break the second. The desktop app then hangs or errors during computer setup; in some setups chat keeps working while the computer never connects. Zscaler is the most common example, and this page uses it for specifics; the same steps apply to any gateway that re signs TLS or buffers responses. This page is for the IT team that runs your gateway. The shared domain list and streaming tests live on Enterprise network configuration; this page covers what Grok Bot adds.
Read More《Cursor Docs》-Connect to private networks
Grok Bot computers run in Cursor's cloud and reach the internet through shared static egress IP addresses. If the systems your Bots need, such as internal APIs, source control, databases, or staging environments, live on a private network, you can connect by installing your organization's networking client on every team computer through Team Setup . Tailscale and Cloudflare Tunnel are common choices, and this page has a worked example for each. Other VPN, zero trust, or mesh clients that run on Linux follow the same pattern. Your services stay off the public internet, and access is governed by the access controls and identity provider you already use.
Read More《Cursor Docs》-Configure identity and access
This guide is for admins running Okta or Microsoft Entra ID. It covers giving people outside your engineering organization access to Grok Bot through your Cursor team, and letting members sign in to IdP provisioned apps from the Bot's computer. For the broader security model, see Grok Bot security.
Read More《Cursor Docs》-Get started with Grok Bot
This guide takes you from install to your first finished task. You'll set up the desktop app, create a Bot with a clear job, and review its work.
Read More《Cursor Docs》-Grok Bot
Grok Bot gives you Bots you can keep around: AI teammates with names, jobs, and context that compounds over time. Each Bot works on a persistent cloud computer with a browser, filesystem, and terminal, so tasks finish in your real tools instead of as chat drafts. Get started with your first Bot, or read how teams roll it out.
Read More